home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Experimental BBS Explossion 3
/
Experimental BBS Explossion III.iso
/
gus
/
digestv5.zip
/
V5N24M.TXT
< prev
next >
Wrap
Text File
|
1994-02-27
|
10KB
|
242 lines
Apparently-To: john.smith@gravis.com
GUS Musician's Digest Sat, 26 Feb 94 4:14 erv Volume 5: Issue 24
Today's Topics:
DIGEST ADMIN: *** READ ME!!! VERY IMPORTANT!!! ***
Dropped notes
GUS Musician's Digest V5 #23
Organizing Custom Patches
Patchmaker Heavy??
Standard Info:
- Meta-info about the GUS can be found at the end of the Digest.
- Before you ask a question, please READ THE FAQ.
----------------------------------------------------------------------
Date: Fri, 25 Feb 1994 16:20:36 -0700 (MST)
From: Dave DeBry <ddebry@dsd.es.com>
Subject: DIGEST ADMIN: *** READ ME!!! VERY IMPORTANT!!! ***
You may have noticed that today's Digests came from a
different site, namely mail.orst.edu. This is a permanent change.
Thanks to Kean Stump for providing a site for the move. Please update
your mail aliases to reflect the following new addresses:
GUS Daily Digest: gus-general-request@mail.orst.edu
Purpose: General Gravis Ultrasound topics.
To post: gus-general@mail.orst.edu
To talk to a human: gus-general-owner@mail.orst.edu
GUS Musician's Digest: gus-music-request@mail.orst.edu
Purpose: For Gravis Ultrasound musicians.
To post: gus-music@mail.orst.edu
To talk to a human: gus-music-owner@mail.orst.edu
GUS Programmer's Digest: gus-sdk-request@mail.orst.edu
Purpose: For Gravis Ultrasound programmers.
To post: gus-sdk@mail.orst.edu
To talk to a human: gus-general-sdk@mail.orst.edu
-------------------------------------------------------------------------
*** GUS WARNING!!! ***
Neither the GUS lists or the list operator are owned or
operated by Gravis. Please don't mail your complaints
concerning the Ultrasound to the list owner. There are
Gravis employees on the lists, so post your problems there.
-------------------------------------------------------------------------
--
Dave ddebry@ debry@ \ "Hey Rocky! Watch me pull a rabbit out of my hat."
DeBry dsd. peruvian. |"Aw, that trick never works."
es. cs.utah. |"Shut up, you damn squirrel! I'm sick and tired
com edu / of your !@%$%& pessimistic attitude!"
------------------------------
Date: Fri, 25 Feb 1994 11:22:09 -0500 (EST)
From: Phat H Tran <ptran@sciborg.uwaterloo.ca>
Subject: Dropped notes
> Date: Thu, 24 Feb 1994 17:11:36 PST
> From: Steve Peddle <speddle@wpg.paramax.com>
> Subject: dropped notes
>
> In a previous digest phat said that the new windows drivers are better ie
> drop less notes? I thought that any dropped midi event would be a
> serious problem. For example notes could get stuck on. Or does better
> mean you can run faster without dropping any notes?
Actually, events don't appear to be dropped, just the occasional notes.
So there's never a stuck note or a missed program change.
BTW, Forte are doing a complete overhaul of the Windows driver (they
changed programmers, I believe) and, hopefully, will squish bugs such
as this one in the process. Don't expect the new drivers to be
released too soon, though.
Phat.
------------------------------
Date: Fri, 25 Feb 1994 10:25:33 -0800
From: chrisw@popserver.stanford.edu (Chris Wilkins)
Subject: Re: GUS Musician's Digest V5 #23
>From: tclee@iss.nus.sg (Lee Teck Chee)
>
>I have compiled a preliminary list of patches that are available on epas
and its
>mirrors. I am arranging them, tentatively, by patch name, archive
containing this
>patch, patch information (ie 8/16-bit, sample rate, number of multisamples),
>suggested replacement (if any), and patch category.
You are doing a great public service! The question is, how will this list be
updated? Are you volunteering to have all people submitting new patches mail
a description to you? (Fine by me).
You've left out a really important one in the properties though: size!
Particularly for modem downloaders and those with < 1M Gusses. Also, you
should probably have looped / unlooped as well as a property.
Also, it would be useful to have cross references for patches which have
something in common. eg. patches which are smaller versions of other
patches. In a similar vein, it would be useful to have something on the
origins of the patches. That is, if they are based on some public samples,
then they should probably say the file so that people know if it's new
waveform material or just new loops and envelopes. (eg. the bosendorfer
piano series). Same thing for samples from synth equipment (if people want
to own up!). All patches based on the same waveform data should really be
grouped together in your list.
>I would like to seek views on how best to define the different categories.
Currently
>I am basing them on GM categories, but this may be quite limiting. Phat has
>suggested that we categorize based on electronic or acoustic and then
subdividing
>those. Any suggestions?
The tricky thing is going to be defining synthy patches I guess, put the
usual sort of bass / lead / pad / FX sort of classification would probably
be O.K.
Chris.
------------------------------
Date: Fri, 25 Feb 94 14:20 MET
From: hst@mh.nl (Klaas Hemstra)
Subject: Re: Organizing Custom Patches
In the previous digest Lee Teck Chee (tclee@iss.nus.sg) sought for
views on how to organize custom patches.
First i would like to say that i think the discussion should really be
about how we can use all these custom patches in a user-friendly
manner. More to the point: How can we program the GUS windows driver
to use the patches from a Standard MIDI file, together with normal
patches. I want to be able to play a MIDI files with a normal windows
application. If one builds such an application (a midi player ?) then
of course you come to the question: "How do i put the right
information in the MIDI file".
To address other patches together with normal GM patches you can:
- Use the bank controler message. But how goes the driver know what
patch should be loaded, and how will you know what patch-bank the
MIDI-file was written for ?
- You can define a SYSEX message that specifies the Patch-NAME for a
certain patch-number. The midi-player should filter the information
and should cause that patch to be loaded in stead of the normal one
for that number.
- A combination of the two above.
I beleive the SYSEX message way is the best. In the case of the GUS,
there will be many patches around, now and in the future. For many
patches (like the TR707 drum set) it will not be likely that they will
be supplied with each MIDI file that uses them. If we define a
patch-bank for the patches that are available NOW it will be out of
date tomorrow. Therefore the patch used in the MIDI file must be linked
to the real patch on disk somehowe, and what is better then in the
MIDI-file itself.
The SYSEX message should define one or more names, in a specific
order, which should be tried in that order. If you also use a patch
number that gives a suitable replacement in case the SYSEX message is
not processed correctly (e.g. the custom patch is NOT found). You have
all the fallback possibilities that are needed.
If you still think that it is necessary to define a patch-bank then
here's my view on that:
My opinion is that you should place patches that simulate the same
instrument in another bank, with the same patch number.
That is the same way that Roland does it in the GS standard.
So if you have a other Trumpet patch, it will be in bank 1 (not bank
0) but with the same patch number (57 wasn't it).
It's a logical way to do it, if it goes wrong with banks you still
have a fairly decent sounding MIDI song.
But what to do with patch-sounds that are not in the current GM set ?
Well, i can think of two ways to do that.
You could allocate a higher bank for that (say bank 8) and put all
those patches in there. That bank should be devided in categories too
like GM, but most likely with other (less specific?) categories.
You can also put them in higher banks within the current GM
categories. So if you have very specific guitar patch not resembling
any of the other guitars you but it at patch 25 of bank 8.
Klaas
------------------------------
Date: Fri, 25 Feb 1994 21:18:16 -0800 (PST)
From: jtcapps@netcom.com (John T. Capps)
Subject: Patchmaker Heavy??
Well, nobody has asked this question yet, so I'll bite.
In the announcement for the 16-bit daughtercard posted here a couple of
days ago, it mentioned (among the other software titles) Patchmaker...NOT
Lite, just Patchmaker. Is this the much awaited upgrade? Will it only
be available with the daughtercard? Am I the only one stewing in
ignorance? :-)
Any info will be appreciated!
John
------------------------------
End of GUS Musician's Digest V5 #24
***********************************
To post to tomorrow's digest: <gus-music@mail.orst.edu>
To (un)subscribe or get help: <gus-music-request@mail.orst.edu>
To contact a human (last resort): <gus-music-owner@mail.orst.edu>
FTP Sites Archive Directories
--------- ------- -----------
Main N.American Site: archive.orst.edu pub/packages/gravis
wuarchive.wustl.edu systems/ibmpc/ultrasound
Main Asian Site: nctuccca.edu.tw PC/ultrasound
European Callers ONLY: theoris.rz.uni-konstanz.de pub/sound/gus
Submissions: archive.epas.utoronto.ca pub/pc/ultrasound/submit
Newly Validated Files: archive.epas.utoronto.ca pub/pc/ultrasound
Mirrors: garbo.uwasa.fi mirror/ultrasound
MailServer For Archive Access: Email to <mail-server@nike.rz.uni-konstanz.de>
Hints:
- Get the FAQ from the FTP sites or the request server.
- Mail to <gus-music-request@mail.orst.edu> for info about other
GUS related mailing lists (general use, programmers, etc.).